Important: The hard disk is not designed to support all features supported by the external storage application and not intended to replace this application in all situations.|
•
|
Important: No hardware changes (PSC, SMC, chassis, etc.) are required to enable the CDR Storage and Retransmission. However, an appropriate software version has to be loaded in the ASR 5000.
Important: Only one CGF server per GTPP group is supported.
|
•
|
CGF configured but not reachable: The ASR 5000 attempts to stream the CDRs to the configured CGF. If the CGF does not respond to queries from ASR 5000 or GTP messages, CDRs will be stored in the internal HDD for future retransmission when CGF becomes reachable again
|
|
•
|
CGF configured and active, then goes down: The ASR 5000 was sending CDRs to CGF (via GTPP) normally. Upon loss of reachability of the CGF, the ASR 5000 determines that CGF is down and starts storing CDRs in its internal HDD.
|
|
•
|
CGF configured, goes down and later becomes available: CDRs were sent (streamed) to CGF until it becomes unreachable. After ASR 5000 determines CGF is down/unreachable, it starts storing CDRs in internal HDD. When CGF becomes available again, CDRs are streamed to CGF, starting from the older CDR first.
|
Important: This feature is disabled by default in the ASR 5000.In GTPP group mode, an option is added to enable this functionality with local-fallback option to existing gtpp storage-server mode in the ASR 5000:
|
•
|
default: Returns the GTPP group configuration to the default ‘remote’ value (the ASR 5000 streams CDRs to the configured external CGF) for the GTPP.
|
|
•
|
If remote is configured, the ASR 5000 sends CDRs to the external CGF. In case CGF is down or unreachable, CDRs will be lost.
|
|
•
|
If local is configured, records are stored in the ASR 5000’s internal hard disk. Mediation / billing system can retrieve the records through Secure FTP (sFTP).
|
|
•
|
If streaming is configured, then the CDRs are sent to CGF by default. If the CGF is down or unreachable, CDRs are temporarily stored in the internal hard disk and streamed to CGF once it becomes available.
|
context <context_name>
cdr [ [ push-interval <interval> ] [ push-trigger space-usage-percent <trigger_percentage> ] [ remove-file-after-transfer ] [ transfer-mode { pull | push primary { encrypted-url <encrypted_url> | url <url> } [ secondary { encrypted-secondary-url <encrypted_secondary_url> | url <secondary_url> } ] } ] [ via local-context ] + | use-harddisk ]
file [ charging-service-name { include | omit } ] [ compression { gzip | none } ] [ current-prefix <string> ] [ delete-timeout <seconds> ] [ directory <directory_name> ] [ edr-format-name ] [ exclude-checksum-record ] [ field-separator { hyphen | omit | underscore } ] [ file-sequence-number rulebase-seq-num ] [ headers ] [ name <file_name> ] [ reset-indicator ] [ rotation [ num-records <number> | time <seconds> | volume <bytes> ] ] [ sequence-number { omit | padded | padded-six-length | unpadded } ] [ storage-limit <limit> ] [ time-stamp { expanded-format | rotated-format | unix-format } ] [ trailing-text <string> ] [ trap-on-file-delete ] [xor-final-record ] +
file [ charging-service-name { include | omit } ] [ compression { gzip | none } ] [ current-prefix <string> ] [ delete-timeout <seconds> ] [ directory <directory_name> ] [ exclude-checksum-record ] [ field-separator { hyphen | omit | underscore } ] [ file-sequence-number rulebase-seq-num ] [ headers ] [name <file_name> ] [ reset-indicator ] [ rotation [ num-records <number> | time <seconds> | volume <bytes> ] ] [ sequence-number { omit | padded | padded-six-length | unpadded } ] [ storage-limit <limit> ] [ time-stamp { expanded-format | rotated-format | unix-format } ] [ trailing-text <string> ] [ trap-on-file-delete ] [udr-seq-num ] [ xor-final-record ] +
|
•
|
The cdr command keywords can be configured either in the EDR or the UDR Configuration Mode. Configuring in one mode prevents the configurations from being applied in the other mode.
|
|
•
|
The use-harddisk keyword is only available on the ASR 5000.
|
To manually push EDR/UDR files to the configured L-ESS, in the Exec mode, use the following command:
|
•
|
The cdr-push command is available in the Exec Mode.
|
|
•
|
<file_name> must be absolute path of the local file to push.
|
This was done with the FTP-enabled account that you configured in the Enabling Charging Record Retrieval section
The following commands use SFTP to log on to a context named ECP as a user named ecpadmin, through an interface configured in the ECS context that has the IP address 192.168.1.10 and retrieve all EDR or UDR files from the default locations:
